Data Access Objects old fashioned? [on hold]

Posted by Bono on Programmers See other posts from Programmers or by Bono
Published on 2014-08-19T13:28:08Z Indexed on 2014/08/19 16:29 UTC
Read the original article Hit count: 210

Filed under:
|
|

A couple of weeks ago I delivered some work for a university project. After a code review with some teachers I got some snarky remarks about the fact that I was (still) using Data Access Objects. The teacher in question who said this mentions the use of DAO's in his classes and always says something along the lines of "Back then we always used DAO's". He's a big fan of Object Relational Mapping, which I also think is a great tool. When I was talking about this with some of my fellow students, they also mentioned that they prefer the use of ORM, which I can understand.

It did make me wonder though, is using DAO's really so old fashioned? I know that at my work DAO's are still being used, but this is due to the fact that some of the code is rather old and therefor can't be coupled with ORM. We also do use ORM at my work.

Trying to find some more information on Google or Stack Exchange sites didn't really enlighten me.

Should I step away from the use of DAO's and only start implementing ORM? I just feel that ORM's can be a bit overkill for some simple projects. I'd love to hear your opinions (or facts) about this.

© Programmers or respective owner

Related posts about programming-practices

Related posts about orm